Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 774f7ba1a35fd023aa0405294d074b6b469cc2b2912749d129f0dbce8656e8b5

Tx prefix hash: 1db8e674c16777cd5385bc35202f10c79d5343480277ab8248483952fb716235
Tx public key: e91523b28e2462acd77372c79058cbfbea1cd5f5c40e0efedd1ab1624b318be1
Timestamp: 1737897480 Timestamp [UCT]: 2025-01-26 13:18:00 Age [y:d:h:m:s]: 00:143:00:53:00
Block: 1205740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101956 RingCT/type: yes/0
Extra: 01e91523b28e2462acd77372c79058cbfbea1cd5f5c40e0efedd1ab1624b318be102110000000d007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a43b266845db1d6da8a8b3162f9ea6ef4a1f401138cc397b7dce31293f14cb9 0.600000000000 1692439 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": 1205750, "vin": [ { "gen": { "height": 1205740 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a43b266845db1d6da8a8b3162f9ea6ef4a1f401138cc397b7dce31293f14cb9" } } ], "extra": [ 1, 233, 21, 35, 178, 142, 36, 98, 172, 215, 115, 114, 199, 144, 88, 203, 251, 234, 28, 213, 245, 196, 14, 14, 254, 221, 26, 177, 98, 75, 49, 139, 225, 2, 17, 0, 0, 0, 13, 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