Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d05ba31030c6c23cecc1257dba1a20f45c9fd3014e55a69bf0fd5e9ac48aa1ff

Tx prefix hash: 96c60f8047f605fbbac48bbb4311f9cb1741b2da060ba8395c03dd3953076faa
Tx public key: 821e29e3dbfecf225336a4f3f7c6e98b9dde29e9bafbd6e777cb2114a7ec1604
Timestamp: 1735673733 Timestamp [UCT]: 2024-12-31 19:35:33 Age [y:d:h:m:s]: 00:113:11:17:53
Block: 1187370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80897 RingCT/type: yes/0
Extra: 01821e29e3dbfecf225336a4f3f7c6e98b9dde29e9bafbd6e777cb2114a7ec160402110000000f007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 148f40a1057d8416ec8cb9afed72cdf5da69c27f93878b11c7dbeda354066bdd 0.600000000000 1673859 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": 1187380, "vin": [ { "gen": { "height": 1187370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "148f40a1057d8416ec8cb9afed72cdf5da69c27f93878b11c7dbeda354066bdd" } } ], "extra": [ 1, 130, 30, 41, 227, 219, 254, 207, 34, 83, 54, 164, 243, 247, 198, 233, 139, 157, 222, 41, 233, 186, 251, 214, 231, 119, 203, 33, 20, 167, 236, 22, 4, 2, 17, 0, 0, 0, 15, 0, 127, 151, 138, 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