Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0d5240f7b5891914a999a4175e330547b056c9776f972b9b07ca35624a6b5f1f

Tx prefix hash: f9b835731bda3112543c7ccfa1a95ef278d222a22ff0c9af09a8bbd1081dde20
Tx public key: 4c08cd56e54d7a691d1cfb08e9faf170b183bd07005e5c8b33700edc88552f6f
Timestamp: 1705592093 Timestamp [UCT]: 2024-01-18 15:34:53 Age [y:d:h:m:s]: 01:306:13:12:37
Block: 938090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477921 RingCT/type: yes/0
Extra: 014c08cd56e54d7a691d1cfb08e9faf170b183bd07005e5c8b33700edc88552f6f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 635785699f7518616abf003ead21b7546a5c20d0b5b2dc5cf2b6010ee4208bd5 0.600000000000 1396156 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 938100, "vin": [ { "gen": { "height": 938090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "635785699f7518616abf003ead21b7546a5c20d0b5b2dc5cf2b6010ee4208bd5" } } ], "extra": [ 1, 76, 8, 205, 86, 229, 77, 122, 105, 29, 28, 251, 8, 233, 250, 241, 112, 177, 131, 189, 7, 0, 94, 92, 139, 51, 112, 14, 220, 136, 85, 47, 111, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8